bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 13 Oct 2023 16:25:00 +0000 (16:25 +0000)
committerAndres Salomon <dilinger@debian.org>
Fri, 13 Oct 2023 16:25:00 +0000 (16:25 +0000)
commitf014f28722d4b7450916680bf8f55045efa9bc49
tree77c3d8f001170dac5276fb279ef156f971066268
parent32a7b624008485d4c22565daf52d232f8ca65ea6
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h